Hello, I am having some trouble setting up my server properly. I'm very new at this, so please excuse my ignorance. We recently had one of our servers crash and had to remove it from AD using NTDSUtil. We currently have only one server which has AD, DNS, DHCP, and some additional services enabled (eventually we are going to use it for NAT as well). There are two NIC ports in use - one connects to our provider and the other connects to our internal network. I am having two problems which I think are related. When I type the command: dcdiag, I get the following error: Starting test: Connectivity The host [GUID]._msdcs.[DOMAIN] could not be resolved to an IP address. Check the DNS server, DHCP, server name, etc. Got error while checking LDAP and RPC connectivity. Please check your firewall settings. ......................... [Domain Controller] failed test Connectivity When I look in the DNS settings, I can't find that GUID. I tried running ipconfig /registerdns and I get the following error: Registration of DNS records failed: Not enough storage space available to complete this operation Here are the results of ipconfig /all Windows IP Configuration Host Name . . . . . . . . . . . . : lcg Primary Dns Suffix . . . . . . . : pcl.princeton.edu Node Type . . . . . . . . . . . . : Hybrid IP Routing Enabled. . . . . . . . : No WINS Proxy Enabled. . . . . . . . : No DNS Suffix Search List. . . . . . : pcl.princeton.edu princeton.edu Ethernet adapter PCL Intranet: Connection-specific DNS Suffix . : pcl.princeton.edu Description . . . . . . . . . . . : Broadcom BCM5709C NetXtreme II GigE (NDIS VBD Client) #2 Physical Address. . . . . . . . . : 00-26-B9-42-D3-77 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes IPv4 Address. . . . . . . . . . . : 192.168.111.5(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : 0.0.0.0 DNS Servers . . . . . . . . . . . : 192.168.111.5 NetBIOS over Tcpip. . . . . . . . : Enabled Ethernet adapter Princeton Network: Connection-specific DNS Suffix . : Princeton.EDU Description . . . . . . . . . . . : Broadcom BCM5709C NetXtreme II GigE (NDIS VBD Client) #3 Physical Address. . . . . . . . . : 00-26-B9-42-D3-79 DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes IPv4 Address. . . . . . . . . . . : 128.112.32.172(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.248.0 Lease Obtained. . . . . . . . . . : Sunday, June 13, 2010 11:10:19 AM Lease Expires . . . . . . . . . . : Monday, June 14, 2010 11:31:12 AM Default Gateway . . . . . . . . . : 128.112.32.1 DHCP Server . . . . . . . . . . . : 128.112.129.111 DNS Servers . . . . . . . . . . . : 128.112.133.220 128.112.128.1 128.112.129.32 Primary WINS Server . . . . . . . : 128.112.128.95 Secondary WINS Server . . . . . . : 128.112.128.97 NetBIOS over Tcpip. . . . . . . . : Enabled If anyone has ideas as to what coudl be wrong. I would greatly appreciate any help that you could offer. Thanks, Andrew

Hello, you should never multihome a Domain controller as you did, one LAN connection and the other one to the internet. See here about: http://msmvps.com/blogs/acefekay/archive/2009/08/17/multihomed-dcs-with-dns-rras-and-or-pppoe-adapters.aspx In your case this create problems as shown about DNS and some more. For correct DNS registration it is important that the DHCP client service is started and set to automatic, even if fixed ip addresses are used, the DHCP client service is required for correct DNS registration with ipconfig /registerdns. Also make sure that the crashed DC is removed from AD sites and services, DNS, etc. see my blog about: http://msmvps.com/blogs/mweber/archive/2010/05/16/active-directory-metadata-cleanup.aspxBest regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

I most definately do not recommend having a multi-homed DC. You are going to have alot of trouble with this design. Its not a good idea. Secondly, I would not recommend using the Windows servers (even less if the server is running as a DC) for a NAT solution. Even though its supported, if you compare the cost of a server/OS license to that off a dedicated router/NAT device, you will find that the Windows solution is not cost effective nor can it provide the same performance and management features. Visit: anITKB.com, an IT Knowledge Base.

I was hitting this error on my Win7 workstation and tried many things like ensuring DHCP Client service was running, etc. I'm sure my DNS server accepts dynamic updates since other Windows 7 hosts on this domain successfully register their names dynamically. Anyway, the root cause of my problem was a registry entry that disables dynamic updates on the client side. The registry key is in HKLM\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters, named DisableDynamicUpdates. See http://technet.microsoft.com/en-us/library/cc778625(v=ws.10).aspx for details. If you have this key with a value of 1, delete the key and retry ipconfig /registerdns. This fixed the problem for me.